Entry points to image-related applications in a mobile device

ABSTRACT

A method and apparatus is provided for operating a mobile device having stored thereon a plurality of applications (“apps”) that are each configured to capture an image. The method includes receiving first user input data requesting invocation of a given one of the applications. The given application is launched by the user. After launching the given application a user interface is presented which serves as an entry point through which all of the image capture applications stored on the mobile device are made available to the user.

CROSS-REFERENCE TO RELATED APPLICATIONS

This application is a continuation of U.S. Ser. No. 13/480,138, filedMay 24, 2012, entitled, “ENTRY POINTS TO IMAGE-RELATED APPLICATIONS IN AMOBILE DEVICE”, which is incorporated herein by reference in itsentirety.

BACKGROUND

With the increasing popularity of mobile devices having image-capturefunctionality, including, for instance, cellphone devices, handhelddevices, handheld computers (e.g., tablets), smartphones and PDAs, thereis a need for improving the user experience by allowing quick access tothe multitude of image-capture and image-processing applications(“apps”) that a user may have downloaded or otherwise installed on theirmobile devices.

For example, specialized image-capture applications exist which applyframes, different filters and lenses and special effects to pictures.For instance, some applications provide double-exposure pictures,panoramic pictures, three-dimensional (3D) pictures or vintage stylepictures.

Therefore, there exists opportunities for improvement in technologies toallow mobile device users quick and convenient access to theirimage-capture and image processing applications

SUMMARY

Apparatus, computer-readable storage media, and methods are disclosedfor allowing mobile device users to easily access all of theirimage-capture applications within the native image-capture applicationwith the click of a button. In one implementation, an application launchbutton is provided which allows a user to launch an image-captureapplication screen which lists all of the image-capture applicationsthat are available to the user on the mobile communication device. Theapplication launch button may be made available in both nativeimage-capture applications (applications provided by the originalequipment manufacturer) and, additionally, in third-party applications.In this way the application launch button serves as an in-context entrypoint to all available image-capture applications, allowing the end userto easily switch from one image-capture application to another.

In one particular implementation the end user can access some or all ofthe image-capture applications with the click of button even when thedevice is locked (i.e., in an above-locked state). However, in somecases the image-capture applications that are available even when themobile device is locked may only provided limited functionality. Thatis, some functions of the applications may be disabled when the mobiledevice is locked.

In another particular implementation, the mobile device can display asimple image representation (e.g., a JPEG or MP4) of an picture that wascaptured in a rich media format. Such rich media formats containadditional information which allows the image to be presented in any ofa variety of formats such as a three-dimensional format or a panoramicformat, for example. In addition, the mobile device may present thesimple representation to the user, along with a link back to theimage-related application that acquired the image. In this way the usercan quickly launch a rich media application both to capture and to viewa complete rich media representation of the image.

This Summary is provided to introduce a selection of concepts in asimplified form that are further described below in the DetailedDescription. This Summary is not intended to identify key features oressential features of the claimed subject matter, nor is it intended tobe used as an aid in determining the scope of the claimed subjectmatter.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1 is a system diagram depicting an exemplary mobile device,including a variety of optional hardware and software components.

FIGS. 2A and 2B illustrate a generalized example of a mobile device,including a touch screen display, image-capture device, proximitysensors, and buttons.

FIG. 3 illustrates a generalized example of a mobile device whileproviding an image-capture application.

FIG. 4 illustrates a generalized example of a mobile device whilepresenting a single point of entry to all available image-captureapplications.

FIG. 5 illustrates a generalized example of a mobile device whileproviding an image-capture application.

FIG. 6 illustrates a generalized example of a mobile device whilepresenting a single point of entry to all available image-captureapplications when the mobile device is in an above-lock state.

FIG. 7 illustrates a generalized example of a mobile device whilepresenting image-capture application settings.

FIG. 8A illustrates a generalized example of a mobile device whilepresenting a lock screen.

FIG. 8B illustrates a generalized example of a mobile device presentingan authentication user interface.

FIG. 9 is a flow chart that outlines an exemplary implementation of thedisclosed technology.

FIG. 10 shows a generalized example of a mobile device presenting abasic representation of a rich media image along with a link back to theapplication (“3D Photo Application”) which captured the image.

DETAILED DESCRIPTION

This disclosure is set forth in the context of representativeembodiments that are not intended to be limiting in any way.

As used in this application and in the claims, the singular forms “a,”“an,” and “the” include the plural forms unless the context clearlydictates otherwise. Additionally, the term “includes” means “comprises.”Further, the term “coupled” encompasses mechanical, electrical,magnetic, optical, as well as other practical ways of coupling orlinking items together, and does not exclude the presence ofintermediate elements between the coupled items.

The described things and methods described herein should not beconstrued as being limiting in any way. Instead, this disclosure isdirected toward all novel and non-obvious features and aspects of thevarious disclosed embodiments, alone and in various combinations andsub-combinations with one another. The disclosed systems, methods, andapparatus are not limited to any specific aspect or feature orcombinations thereof, nor do the disclosed things and methods requirethat any one or more specific advantages be present or problems besolved.

Although the operations of some of the disclosed methods are describedin a particular, sequential order for convenient presentation, it shouldbe understood that this manner of description encompasses rearrangement,unless a particular ordering is required by specific language set forthbelow. For example, operations described sequentially may in some casesbe rearranged, omitted, or performed concurrently. Moreover, for thesake of simplicity, the attached figures may not show the various waysin which the disclosed things and methods can be used in conjunctionwith other things and methods. Additionally, the description sometimesuses terms like “produce,” “generate,” “select,” “capture,” and“provide” to describe the disclosed methods. These terms are high-levelabstractions of the actual operations that are performed. The actualoperations that correspond to these terms can vary depending on theparticular implementation and are readily discernible by one of ordinaryskill in the art.

Any of the disclosed methods can be implemented as computer-executableinstructions stored on one or more computer-readable storage media(e.g., non-transitory computer-readable media, such as one or morevolatile memory components (such as DRAM or SRAM), or nonvolatile memorycomponents (such as hard drives)) and executed on a computer (e.g., anycommercially available computer, including smart phones or other mobiledevices that include computing hardware). Any of the computer-executableinstructions for implementing the disclosed techniques as well as anydata created and used during implementation of the disclosed embodimentscan be stored on one or more computer-readable storage media (e.g.,non-transitory computer-readable storage media). The computer-executableinstructions can be part of, for example, a dedicated softwareapplication or a software application that is accessed or downloaded viaa web browser or other software application (such as a remote computingapplication). Such software can be executed, for example, on a singlelocal computer (e.g., any suitable commercially available computer) orin a network environment (e.g., via the Internet, a wide-area network, alocal-area network, a client-server network (such as a cloud computingnetwork), or other such network) using one or more network computers.

The disclosed method allow third party developers to access severalservices that augment the user experience and supply basic userinterface and Application Programming Interface (API) capabilities tothe developers, allowing them to efficiently create applications thatare compatible with the system. As used herein, the term “service”refers to a utility, function or program code module that performs sometask for a calling process, which has no user interface and which isaccessed programmatically through a call interface such as an API.

For clarity, only certain selected aspects of the software-basedimplementations are described. Other details that are well known in theart are omitted. For example, it should be understood that the disclosedtechnology is not limited to any specific computer language or program.For instance, the disclosed technology can be implemented by softwarewritten in C++, Java, Perl, JavaScript, HTML5, or any other suitableprogramming language. Likewise, the disclosed technology is not limitedto any particular computer or type of hardware. Certain details ofsuitable computers and hardware are well known and need not be set forthin detail in this disclosure.

Furthermore, any of the software-based embodiments (comprising, forexample, computer-executable instructions for causing a computer toperform any of the disclosed methods) can be uploaded, downloaded, orremotely accessed through a suitable communication means. Such suitablecommunication means include, for example, the Internet, the World WideWeb, an intranet, software applications, cable (including fiber opticcable), magnetic communications, electromagnetic communications(including RF, microwave, and infrared communications), electroniccommunications, or other such communication means.

Theories of operation, scientific principles or other theoreticaldescriptions presented herein in reference to the apparatus or methodsof this disclosure have been provided for the purposes of betterunderstanding and are not intended to be limiting in scope. Theapparatus and methods in the appended claims are not limited to thoseapparatus and methods that function in the manner described by suchtheories of operation.

In the following description, certain terms may be used such as “up,”“down,” “upper,” “lower,” “horizontal,” “vertical,” “left,” “right,”“over,” “on,” “near,” and the like. These terms are used, whereapplicable, to provide some clarity of description when dealing withrelative relationships. But, these terms are not intended to implyabsolute relationships, positions, and/or orientations.

As used in this disclosure, above-lock means that a device is in a statewhere at least some functions of the device are not accessible to a useras a result of the device being in the above-lock (or “locked”) state.As used in this disclosure, below-lock means that a device is in a statewhere additional functionality is available that is not accessible to auser in the above-lock state. In addition, a device may be described ashaving other states that are not necessarily mutually exclusive with theabove-lock or below-lock authentication states. For example, in someembodiments, a device can be in either a low-power state or an activestate while concurrently being in an above-lock state. Similarly, insome embodiments, a device can be in a below-lock state whileconcurrently being in a low-power or active state.

Software applications, sometimes referred to as “apps” in the market,constitute a driver for the sale and popularity of mobile devices. Thecomputing power and functionality of mobile devices are often used todownload and use the applications available for download from variouswebsites. Applications are generally executable programs that aredownloaded and executed on the mobile device to perform variousfunctions, such as to provide sports news, access to electronic mail(email), access to the Global Positioning System (GPS), playing videogames, playing music and video, and the like.

As used herein, the term “image-related application” will be used torefer to an application that can capture an image and/or process animage. That is, both an image-capture application and animage-processing application may be referred to as an image-relatedapplication. Moreover, since video may be treated as a sequence of stillimages, the terms “image” and “video” will often be used interchangeablywith one another unless the context clearly indicates otherwise.

As previously mentioned, users now have access to many image-captureapplications, and consequently often download several such image-relatedapplications for use in different circumstances. To gain access to theseapplications the user typically has to locate the application ofinterest among all the other applications stored on the mobile device.Searching for a particular image-related application that is mixed notonly with other image-related applications but also with other types ofapplications can make it difficult to find the image-related applicationof interest. This process can become unwieldy and extend the time neededbefore the user can take a picture, which can be inconvenient and evencause the user to miss capturing a desired image.

The disclosed technology relates to the accessibility of image-relatedapplications on a mobile device. Certain embodiments of the disclosedtechnology permit the end user to easily access all of theirimage-related applications within the native image-related applicationwith the click of a button. Another exemplary approach allows the enduser to access at least a subset of the image-related applications withthe click of button even when the device is locked.

While reference is made throughout this document to image-capture appsor applications, more generally the disclosed technology relates to anyexecutable code segments that are capable of acquiring an image. Forinstance, the image acquisition functionality may be implemented using adynamic link library (DLL) that is hosted in another application.

I. Example Mobile Device

FIG. 1 is a system diagram depicting an exemplary mobile device 100including a variety of optional hardware and software components, showngenerally at 102. Any components 102 in the mobile device cancommunicate with any other component, although not all connections areshown, for ease of illustration. The mobile device can be any of avariety of computing devices (e.g., cell phone, smartphone, tablet orother handheld computer, Personal Digital Assistant (PDA), etc.) and canallow wireless two-way communications with one or more mobilecommunications networks 104, such as a cellular or satellite network.

The illustrated mobile device 100 can include a controller or processor110 (e.g., signal processor, microprocessor, ASIC, or other control andprocessing logic circuitry) for performing such tasks as signal coding,data processing, input/output processing, power control, and/or otherfunctions. An operating system 112 can control the allocation and usageof the components 102, including power states, above-lock states, andbelow-lock states, and provide support for one or more applicationprograms 114. The application programs can include common mobilecomputing applications (e.g., image-related applications, emailapplications, calendars, contact managers, web browsers, messagingapplications), or any other computing application.

The illustrated mobile device 100 can include memory 120. Memory 120 caninclude non-removable memory 122 and/or removable memory 124. Thenon-removable memory 122 can include RAM, ROM, flash memory, a harddisk, or other well-known memory storage technologies. The removablememory 124 can include flash memory or a Subscriber Identity Module(SIM) card, which is well known in GSM communication systems, or otherwell-known memory storage technologies, such as “smart cards.” Thememory 120 can be used for storing data and/or code for running theoperating system 112 and the application programs 114. Example data caninclude web pages, text, images, sound files, video data, or other datasets to be sent to and/or received from one or more network servers orother devices via one or more wired or wireless networks. The memory 120can be used to store a subscriber identifier, such as an InternationalMobile Subscriber Identity (IMSI), and an equipment identifier, such asan International Mobile Equipment Identifier (IMEI). Such identifierscan be transmitted to a network server to identify users and equipment.

The mobile device 100 can support one or more input devices 130 forresponding to inputs from users and other sources. Such input devicesmay include a touch screen 132, microphone 134, camera 136, physicalkeyboard 138, trackball 140, and/or proximity sensor 142, and one ormore output devices 150, such as a speaker 152 and one or more displays154. Other possible output devices (not shown) can include piezoelectricor haptic output devices. Some devices can serve more than oneinput/output function. For example, touch screen 132 and display 154 canbe combined into a single input/output device.

In some implementations the various input devices 130 may supportnatural user interface (NUI) methods. Examples of NUI methods includethose relying on speech recognition, touch and stylus recognition,gesture recognition both on screen and adjacent to the screen, airgestures, head and eye tracking, voice and speech, vision, touch,gestures, and machine intelligence. Specific categories of NUItechnologies on which Microsoft is working include touch sensitivedisplays, voice and speech recognition, intention and goalunderstanding, motion gesture detection using depth cameras (such asstereoscopic camera systems, infrared camera systems, rgb camera systemsand combinations of these), motion gesture detection usingaccelerometers/gyroscopes, facial recognition, 3D displays, head, eye,and gaze tracking, immersive augmented reality and virtual realitysystems, all of which provide a more natural interface, as well astechnologies for sensing brain activity using electric field sensingelectrodes (EEG and related methods).

A wireless modem 160 can be coupled to an antenna (not shown) and cansupport two-way communications between the processor 110 and externaldevices, as is well understood in the art. The modem 160 is showngenerically and can include a cellular modem for communicating with themobile communication network 104 and/or other radio-based modems (e.g.,Bluetooth 164 or Wi-Fi 162). The wireless modem 160 is typicallyconfigured for communication with one or more cellular networks, such asa GSM network for data and voice communications within a single cellularnetwork, between cellular networks, or between the mobile device and apublic switched telephone network (PSTN).

The mobile device can further include at least one input/output port180, a power supply 182, a satellite navigation system receiver 184,such as a Global Positioning System (GPS) receiver, an accelerometer186, a gyroscope (not shown), and/or a physical connector 190, which canbe a USB port, IEEE 1394 (FireWire) port, and/or RS-232 port. Theillustrated components 102 are not required or all-inclusive, as anycomponents can be deleted and other components can be added.

FIG. 2A depicts a front view 210 of an example mobile device 200, whileFIG. 2B depicts a rear view 250 of the mobile device. As shown, themobile device 200 includes several hardware buttons, including a homebutton 220, a power button 222, and a camera shutter (image-capture)button 224. Also depicted is a touch screen display 230, which is showndisplaying a touch screen unlock button 232, a touch screen camerashutter button 234, and a locked-mode indicator 236.

The mobile device 200 includes a microphone 240 and speaker 242, alongwith two proximity sensors 246 and 248, situated below the surface ofthe mobile device. In some examples, a single, or three or more,proximity sensors can be used. Any suitable proximity sensor(s) can beemployed. In some examples, the proximity sensors 246 and 248 emit aninfrared beam and receive a reflected infrared beam, which is reflectedoff the surface of a nearby object that has been illuminated by theemitted infrared beam. An intensity measurement, or other measuredproperty for the received beam, can be used to determine whether anobject is in proximity with the mobile device 200.

In other examples, an image sensor coupled with a camera lens 260 can beused as a light sensor to detect an object in proximity with the mobiledevice 200. For example, objects in proximity with the mobile device 200can be determined using light received through the camera lens 260 withan image sensor based on CMOS, CCD (charge-coupled device), or othersuitable technology. In some examples, only a few rows, columns, orpixels of the image sensor are active when checking proximity, in orderto reduce power consumption.

The camera shutter button 224 of the mobile device 200 may be adedicated dual-action camera shutter button, with the ability to detect“half-press” and “full-press” as distinct, separate actions. As isreadily understood to those of skill in the art, a half-press refers tothe partial actuation of a button or other control, while a full-pressrefers to a further actuation of the button or control past a determinedlimit. In some examples, the dual action camera shutter button 224 isassociated with the following attributes. When a half-press is detected,input data is received with the mobile device that is associated withauto-focus functionality. When a full-press is detected, input data isreceived that is associated with camera invocation and image capture. Insome examples, the end user can set an option to determine whether ornot input data resulting from a half-press or full-press of the camerabutton initiates functionality when, e.g., the display 230 is turned offor the device is in standby mode. While the camera shutter button 224 isshown located on a front surface 205 of the mobile device 200, in otherexamples, a camera shutter button can be positioned at alternatelocations. For example, the camera shutter button 224 can be located atlocation 225 (on a side surface 206) or location 226 (on a rear surface207), respectively, of the mobile device.

Turning to the rear view 250 shown in FIG. 2B, the example mobile device200 includes the camera lens 260 and an electronic flash 265. In someexamples, there is no flash present in the mobile device 200. Theindividual components (e.g., the hardware buttons 220, 222, and 224,microphone 240, speaker 242, touch screen display 230, camera lens 260and flash 265) can be coupled to a mobile device chassis (not shown),which is connected to internal components of the mobile device 200, forexample: one or more processors, a piezoelectric actuator, a powersupply, and a modem.

As shown in FIGS. 2A and 2B, there are several considerations that canbe made in the placement of components on the mobile device 200, such asthe home button 220, power button 222, camera shutter button 224, thecamera lens 260, electronic flash 265, proximity sensors 246 and 248,and the photodiode 280. For example, it is desirable that the placementof the camera shutter button 224 enables or even encourages a user tonaturally position the mobile device 200 in a landscape position whencapturing images. It is also desirable that the camera shutter button224 be positioned such that operation of the button is facilitated usingan index finger or thumb. For example, the camera shutter button 224 asshown can be easily accessed with a user's right thumb while capturingan image with the mobile device 200 in a landscape position. In otherexamples, the camera shutter button 224 can be moved to other suitablepositions, for example, locations 224 or 226. It is also desirable thatthe camera shutter button 224 and/or power button 222 be positioned toavoid accidental actuation, in order to mitigate the chance that animage capture application will be launched inadvertently.

It should be noted that any reference herein to a button may refer to aphysical or virtual button. Moreover, more generally, instead of abutton, any suitable user interface may be provided to receive userinput data.

II. Example Mobile Device Image Capture Application

FIG. 3 depicts a front view 310 of an example mobile device 300 aftercapturing an image 315 using a camera (not shown) coupled to the mobiledevice. The image may be been captured using a native application or athird party application. As shown, the display 305 of the mobile device300 includes buttons or controls 330, 332, 334, 336, 338, 370, 372, 374,376 and 378, which can be used to control the image-capturefunctionality. These controls include a still image capture mode button330 (highlighted to indicate that still capture is the currentlyselected capture mode), a video capture mode control 332, zoom-in andzoom-out controls 384 and 336, an options control button 338, emailimage button 370, save image button 372, upload image button 374, deleteimage button 376 and application launch button 378.

The mobile device 300 also includes several hardware buttons, includinga camera shutter button 342 located on a side surface of the mobiledevice, as well as a search button 344, a home button 346, and a backbutton 348, which are located on a front surface of the mobile device.These hardware buttons 342, 344, 346, and 348 can be used for invokingand/or executing various operations using the mobile device 300. Forexample, camera shutter button 342 can be used for invoking and/orexecuting an image capture application, as well as controlling functionswithin the image capture application, such as autofocusing and/oroperating a camera shutter. Search button 344 can be used to invokeand/or execute a user interface for searching data. Home button 346 canbe used for navigating software functionality on the mobile device 300by, for example, setting the mobile device to a home screen state, orinvoking other assigned functionality. Back button 348 can be used fornavigating software functionality by, for example, requesting apreviously requested object that was viewed using the mobile device 300.

Application launch button 378 is used to launch or otherwise execute animage-related application screen which lists or otherwise presents allthe image-related applications that are available to the user on themobile communication device. The end user may execute or launch theapplications directly from the screen. These image-related applicationsmay include both native image-related applications as well as thirdparty image-related applications. In this way application launch button378 serves as an in context entry point to all available image-relatedapplications, allowing the end user to easily switch from oneimage-related application to another. For an application to be includedin this presentation of image-related applications, developers may berequired to include in their image-related applications suitable APIcalls or the like which bring up the image-related application screen.

FIG. 4 shows an example of an image-capture screen 405 that may bepresented to the user on the display of mobile device 400 after pressingbutton 378. The image-related applications which are listed in thisexample include the native camera application, Panorama, Contoso,Litware, Superlense, Bing Vision, Fabrikam, Night Cam and Prosware Lite.In addition to serving as a single point of entry to all availableimage-related applications, image-related application screen 405 mayallow the end user to perform other functions. For example, as shown, alink may be provided (designated in FIG. 4 as “find more camera apps”)which directs the user to an application marketplace from which the usercan purchase or otherwise obtain additional image-related applications.In addition, in some embodiments the screen 405 may allow the user todesignate one of the image-related applications, including any of thethird-party applications, as the default application or as one of ashort list of “favorites.”

Referring again to FIG. 3, the mobile device 300 is shown displaying anexample “camera roll” application, which allows a user to seepreviously-captured images (e.g., images 315 and 360) by sliding afinger 390 in the direction shown by the arrow 392, which moves images315 and 360 in the direction of finger motion across the display 305. Asshown, film “sprocket holes” can be displayed on the images 315 and 360to emphasize the camera roll metaphor (e.g., displaying images in astrip similar to a traditional film camera). Using a camera roll allowsa user to swipe a finger across a touch screen and thereby move theimage in the direction of the swipe (or a drag or flip) and allows auser to see previously taken photos.

Although the controls described above in connection with FIGS. 3 and 4are shown as being displayed on a touch screen, some or all of thecontrols can be implemented using hardware buttons or other userinterface devices, including any of the aforementioned NUIs.

As previously mentioned, in some implementations the end user is able toaccess some or all of the image-related applications with the click of abutton (physical or virtual) even when the device is locked. That is, inthese embodiments the button 378 can be used to access predeterminedones of the image-related applications in an above-lock mode. In someembodiments the image-related applications that are available above-lockmay be specified by the end user or, in an enterprise environment, by acorporate IT department.

FIG. 6 shows an example of a screen 420 on mobile device 400 that may bepresented to the user after pressing application launch button 378 whenthe camera is in above-lock mode. A distinct icon is superimposed overthose image-related applications which are unavailable above-lock. Inthis example the Superlense and Fabrikam applications are not availableabove-lock.

As shown in FIG. 5, the mobile device 300 is depicted after capturing animage 315 using a camera (not shown) coupled to the mobile device whilethe device was in above-lock mode. As shown, the display 305 of themobile device 300 also includes an above-lock indicator 320, along withcontrols 330, 332, 334, 336, and 338, which can be used to control asubset of the image-capture functionality available in below-lock mode.It should be noted that other controls which are available in abelow-lock mode (see FIG. 3) are not available in above-lock mode. Inparticular, in this example, email image button 370, save image button372, upload image button 374, and delete image button 376 are notavailable in above-lock mode. However, in this example applicationlaunch button 378 is available above-lock to launch a screen whichpresents all the image-related applications that are available to theuser on the mobile communication device when in above-lock mode.

Examples of functionality that may be allowed by an image-relatedapplication when the mobile device is in the above-lock state mayinclude one or more of the following: functionality associated with theviewfinder (capture mode) of an image-related application to providephoto capture, video capture, display of a most-recently capturedphotograph (i.e., a “confirmation image”), and adjustment ofimage-capture settings, such as flash, zoom, autofocus, white balance,and other such image operations. The available viewfinder functionalityin the above-lock state typically includes operations that would notcompromise a user's privacy if accessed by an authenticated user.

Furthermore, other functionality normally available in below-lockstate(s) can be disabled in above-lock state(s). For example,auto-upload of images can be disabled in the above-lock state to preventaccidently- or undesirably-captured photographs from being uploaded to aremote server or computing cloud. Other functions that may be disabledinclude delete image, send to, use as, view image gallery, and othersuch private image operations.

An image-related application, or certain functionality provided by animage-related application, may not be available above-lock if itrequires other capabilities of the mobile device which are unavailablein an above-lock mode. For instance, this may occur if an image-relatedapplication requires access to an e-mail or contacts application, whichare themselves not available in an above-lock mode.

In some examples, the user can proceed to an authentication screen fromthe above-lock limited-feature image-related application, and, afterbeing successfully authenticated, return to the full-featuredapplication that is available only when in a below-lock state.

III. Example Mobile Device Settings

FIG. 7 depicts an example of a mobile device displaying an optionsscreen 430. The options screen 430 provides a menu that allows the userto specify which image-related applications, if any, may be availableabove-lock. In this example the end user has indicated that theSuperlens application is to be available above-lock. In addition, forsecurity reasons, an IT policy requires that the Night Cam applicationis only to be made available with a password. Accordingly, thisapplication is grayed out and the end user is not able to select it foruse above-lock.

IV. Image-Related Applications Employing Rich Media Data

Image-related applications are now available which acquire data not onlyin basic video formats such as JPEG and MP4, for example, but which alsoacquire and store additional backing data associated with the acquiredimages. For instance, an image-related application that renders athree-dimensional image generally stores JPEG data and backing data thatis used to form a three-dimensional model from the JPEG data. Similarly,an image-related application that renders a panoramic image generallystores JPEG data and backing data that is used to form the panoramicimage from one or more JPEG images. Accordingly, the basic video dataalong with the associated backing data, which may be referred to as richmedia data, is used to present the image in the intended manner (e.g.,as a three-dimensional image or a panoramic image).

In some embodiments of the disclosed technology the camera roll, whichallows the user to see previously-captured images, is only capable ofsaving and presenting data in one of the basic image and video formats.Consequently, the camera roll may not be able to render the images asintended using the rich media data. Rather, the camera roll may only beable to render a representation that uses the basic image and videoformat portion of the rich media data. In this case the camera roll maypresent the basic (e.g., JPEG, MP4) representation to the user, alongwith a link back to the image-related application that acquired theimage. For instance, FIG. 10 shows a basic representation of a richmedia image along with a link 645 back to the application (“3D PhotoApplication”) which captured the image. In this way the user can quicklyview the complete rich media representation of the image though theimage-related application. Moreover, in this way the camera roll can nowserve as a single entry point for all images, whether or not theyinclude rich media data. As a result the user can render a completerepresentation of the image without having to search through all of theapplications available on the mobile device simply to find theapplication that acquired the image. If the rich media data is storedseparately from the data in the basic representation, some scheme (suchas the use of a unique identifier) may be used to re-associate the twotypes of data when the rich media representation is to be rendered.

In addition to viewing the basic representation without accessing theoriginal application, the user may be able to share the basicrepresentation using conventional sharing applications.

V. Lock and Authentication Screens

As discussed above, certain image-related applications, and/or somefunctions offered by certain image-related applications, may not beavailable in an above-lock mode. If a user attempts to access such anapplication or function while above-lock, the application may make acall to the unlock dialog box API to switch to a below-lock mode. Thiscall brings up one or more screens that allow the user to unlock themobile device. An example of such a screen is shown in FIGS. 8A and 8B.

FIG. 8A depicts a mobile device 500 having a touch screen display 510,which is displaying a lock screen 515, including an unlock slidercontrol 520. A mobile device user can slide/drag a finger 525 in thedirection indicated by the arrows displayed with the unlock slidercontrol 520 (finger motion is in either of the directions indicated bythe arrow 522) in order to request the device to present anauthentication screen, for example, as shown in FIG. 8B. Although theauthentication screen shown in FIG. 8B uses a PIN pad, other techniquescan be used, for example, fingerprint or voice recognition.

FIG. 8B depicts the mobile device 500 of FIG. 8A after the user slides afinger on the unlock slider control 520. As shown, the mobile device 500presents an authentication screen 530 including a PIN pad 540 on thetouch screen display 510. The user can enter a PIN (e.g., a four-digitsequence of numerals) using a finger 550 on the pin pad 540. If the PINentered matches a stored PIN, the user is successfully authenticated,and the device can enter a below-lock (unlocked) state.

One the device enters the below-lock state the user will be returned tothe application that the user was attempting to access in the above-lockstate. At this point, however, the full functionality of the applicationwill now be available.

VI. Example Invocation of Image-Related Application

FIG. 9 is a flow chart 600 that outlines an illustrative method ofoperating a mobile device having stored thereon a pluralityimage-related applications. At process block 610, user input data isreceived requesting invocation of an application. For example, a mobiledevice can receive input data from an input source such as one or morehardware buttons, a touch screen, a microphone, or a natural userinterface. The application requested is an image-related applicationsuch as a camera or video capture application. At decision block 620 adetermination is made as to whether the mobile device is in a below-lockor above-lock state. If it is in the below-lock state, the applicationis launched at block 630. If the device is in the above-lock state, adetermination is made at block 640 as to whether a user or other partyhas designated the application as being one that is availableabove-lock. This designation may have been made by the user though anappropriate settings or options control. If the application is availableabove-lock, then the application is executed or launched at block 680.Even if the application is available above-lock, a user may havedesignated that only a subset of its functionality is to be madeavailable. If the application is not available above-lock, at block 650the user may be presented with a user interface through which the userhas the option of entering the below-lock state. In some examples, theuser interface may be a key, button, or a set of key presses or touchscreen gestures on a touch-display. If the user does not enter thebelow-lock state, then the application cannot be executed and processends at block 670. On the other hand, if the user decides to enter thebelow lock state, then the application is launched at block 680. Oncethe application is launched, then at block 690 the application presentsa user interface from which the user can access any other availableimage-related application. The user interface may be, for example, akey, button, or a set of key presses or touch screen gestures on atouch-display.

The disclosed methods, apparatus, and systems should not be construed aslimiting in any way. Instead, the present disclosure is directed towardall novel and nonobvious features and aspects of the various disclosedembodiments, alone and in various combinations and subcombinations withone another. The disclosed methods, apparatus, and systems are notlimited to any specific aspect or feature or combination thereof, nor dothe disclosed embodiments require that any one or more specificadvantages be present or problems be solved. The techniques andsolutions described in this application can be used in variouscombinations to provide an improved user experience with mobile devices,including mobile devices such as smart phones.

Any of the methods described herein can be performed via one or morenon-transitory computer-readable media (e.g., storage or other tangiblemedia) comprising (e.g., having or storing) computer-executableinstructions for performing (e.g., causing a computing device toperform) such methods. Operation can be fully automatic, semi-automatic,or involve manual intervention.

Having described and illustrated the principles of our innovations inthe detailed description and accompanying drawings, it will berecognized that the various embodiments can be modified in arrangementand detail without departing from such principles. For example, anytechnologies described herein for capturing still photos can also beadapted for capturing video. It should be understood that the programs,processes, or methods described herein are not related or limited to anyparticular type of computing environment, unless indicated otherwise.Various types of general purpose or specialized computing environmentsmay be used with or perform operations in accordance with the teachingsdescribed herein. Elements of embodiments shown in software may beimplemented in hardware and vice versa.

In view of the many possible embodiments to which the principles of thedisclosed invention may be applied, it should be recognized that theillustrated embodiments are only preferred examples of the invention andshould not be taken as limiting the scope of the invention. Rather, thescope of the invention is defined by the following claims. We thereforeclaim as our invention all that comes within the scope of these claimsand their equivalents.

1-20. (canceled)
 21. A method of operating a mobile device having storedthereon a plurality of applications that are each configured to captureand/or process an image, the method comprising: receiving a user requestthrough a first user interface in a launched first application todisplay previously-captured images; displaying the previously-capturedimages including rich media type images, the rich media type imagesstored in a rich media data format including basic image data andassociated backing data used to render the rich media data type images,wherein the rich media type images are displayed via the launched firstapplication in a format that does not include all of the rich mediadata; and providing a link with the basic image data for at least one ofthe rich media type images, the link operable to invoke a secondapplication of the plurality of applications, the second applicationbeing an application that captured the corresponding rich media typeimage and capable of displaying the rich media type image in a formatthat includes all of the rich media data format including basic imagedata and associated backing data.
 22. The method of claim 21 furthercomprising presenting the first user interface on a touch screen of themobile device.
 23. The method of claim 22 in which the first userinterface includes a virtual button.
 24. The method of claim 23 in whichthe virtual button is presented by the first application.
 25. The methodof claim 21 wherein the basic image data is represented as a JPEG image.26. The method of claim 25 wherein the basic image data and associatedbacking data are used to render a panoramic image.
 27. The method ofclaim 25 wherein the basic image data and associated backing data areused to render a three-dimensional image.
 28. The method of claim 21 inwhich the plurality of applications includes at least one nativeimage-related application and at least one third party image-relatedapplication.
 29. The method of claim 21 in which the first userinterface is available for presentation to the user when the mobiledevice is in an above-lock state.
 30. The method of claim 21 in whichpredetermined ones of the plurality of applications are unavailable whenthe mobile device is in an above-lock state.
 31. The method of claim 21in which activation of an application launch button from a userinterface provides an indication of all of the plurality ofimage-related applications and which of the plurality of applicationsare unavailable when the mobile device is in an above-lock state. 32.The method of claim 21 in which one or more functions of the firstapplication available in a below-lock state are unavailable to the userof the mobile device while the mobile device is in the above-lock state.33. The method of claim 32 further comprising: receiving second inputdata requesting one of the unavailable functions; and based on thesecond input data, presenting a third user interface to the useroperable to change the state of the mobile device to the below-lockstate.
 34. The method of claim 21 in which the first application is athird party application.
 35. An apparatus, comprising: an image capturedevice; a user interface; one or more processors; and one or morecomputer-readable storage media storing a plurality of image-relatedapplications for capturing and/or processing an image, said computerreadable storage media further storing computer-readable instructionsthat when executed by the processors, cause the apparatus to present, inresponse to a user request received by the user interface, an entrypoint through which all of the image capture applications stored on thecomputer readable storage media are available to the user.
 36. Theapparatus of claim 35 in which the user interface provides a link to anapplication marketplace from which additional applications can beacquired.
 37. The apparatus of claim 35 in which the image captureapplications stored on the computer readable storage media include atleast one third party image-related application, said computer readablestorage media further storing computer-readable instructions that whenexecuted by the processors, cause the apparatus to establish the thirdparty image-related application as a default application in response toa user request received by the user interface.
 38. One or morecomputer-readable storage media storing computer-readable instructionsthat when executed by a computer cause the computer to perform a methodof operating a mobile device having a plurality of authenticationstates, including an above-lock state and an below-lock state, themethod comprising: executing a first image-related application; anddisplaying, on a touch-screen made available by the first image-relatedapplication, a listing of all other image-related applications currentlyavailable for execution by the mobile device in at least the below-lockstate, each of the other image-related applications being selectable forexecution from the touch-screen.
 39. The one or more computer-readablestorage media of claim 38 in which at least one of the image-relatedapplications is available in an above-lock state.
 40. The one or morecomputer-readable storage media of claim 39 in which the at least oneimage-related application is a third-party image-related application, asubset of functionality available from the third party image-relatedapplication being unavailable in the above-lock state.